Add policy result types and diagnostic metadata plumbing#38515
Draft
dsa0x wants to merge 2 commits intopolicy-pr1-foundationfrom
Draft
Add policy result types and diagnostic metadata plumbing#38515dsa0x wants to merge 2 commits intopolicy-pr1-foundationfrom
dsa0x wants to merge 2 commits intopolicy-pr1-foundationfrom
Conversation
This was referenced May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is part of a stacked series to upstream the policy work in smaller, reviewable pieces:
This PR adds the shared Terraform-side types needed to carry policy evaluation results through planning and execution, along with the diagnostic plumbing needed to preserve policy metadata and source context.
Included here
plans.PolicyResultsTarget Release
1.16.x
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry